This is necessary because the repos in the ipfs-examples org use an npm script named 'test:example' instead of just 'test', right?

I'm not against this change, but why not just use 'test'?

Hi @achingbrain,

Yes, some examples, e.g.: react, vue, nextjs, have their proper test scripts. If someone wants to use the standalone repo from, for example, vue, to create an app the only step the user needs to "clean" the repo is removing the test:example and the test folder

I think they'll need to do a bit more as it stands so I'm not sure it's that simple. For example playwright is a dev dep of these projects that would need removing too, plus any other dev deps used by the existing test scripts.

If the idea is that you'd use the react, vue etc testing tools after forking the example, the example should really use those tools in the first place so the user has nothing to remove or clean up.

Since they don't currently, I'd propose that as a further work item, rename 'test:example' to 'test' in the examples and make the suggested changes to ipfs/js-ipfs#3821 so we can get it merged and come back to the testing framework problem.

@achingbrain

I've already made the suggested changes, I'm just waiting for this PR ipfs-examples/js-ipfs-examples#26 to have the test script in every example

Will do, thanks @achingbrain